Skip to content

deps: bump node to v22.16.0 #93080

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Jun 16, 2025
Merged

deps: bump node to v22.16.0 #93080

merged 19 commits into from
Jun 16, 2025

Conversation

JonasBa
Copy link
Member

@JonasBa JonasBa commented Jun 6, 2025

@JonasBa JonasBa requested review from a team as code owners June 6, 2025 22:27
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 6, 2025
@JonasBa JonasBa requested a review from a team June 6, 2025 22:27
@JonasBa
Copy link
Member Author

JonasBa commented Jun 6, 2025

@joshuarli what is the process for updating the mirror and shasum? I've updated the shasum to match the files available from node, but I'm currently getting a 404 from our mirror

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 11, 2025
Copy link
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

Copy link
Member

@joshuarli joshuarli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i've updated this PR to use .node-version!

Copy link

codecov bot commented Jun 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #93080       +/-   ##
===========================================
+ Coverage   46.37%   88.08%   +41.70%     
===========================================
  Files       10309    10330       +21     
  Lines      594899   595883      +984     
  Branches    23130    23126        -4     
===========================================
+ Hits       275905   524899   +248994     
+ Misses     318501    70491   -248010     
  Partials      493      493               

@natemoo-re
Copy link
Member

I'm working on the CI failures—just a resolution issue with a node-style specifier in the rspack config.

@joshuarli joshuarli merged commit 4df68a9 into master Jun 16, 2025
69 checks passed
@joshuarli joshuarli deleted the jb/node/24 branch June 16, 2025 18:59
@asottile-sentry asottile-sentry added the Trigger: Revert Add to a merged PR to revert it (skips CI) label Jun 16, 2025
@getsentry-bot
Copy link
Contributor

PR reverted: 0aeb212

getsentry-bot added a commit that referenced this pull request Jun 16, 2025
This reverts commit 4df68a9.

Co-authored-by: asottile-sentry <[email protected]>
JonasBa added a commit that referenced this pull request Jun 16, 2025
joshuarli pushed a commit that referenced this pull request Jun 16, 2025
Reapply node version bump, but preserve .volta.json so we can maintain
backcompat with getsentry
getsentry-bot added a commit that referenced this pull request Jun 16, 2025
JonasBa added a commit that referenced this pull request Jun 17, 2025
JonasBa added a commit that referenced this pull request Jun 17, 2025
…3698)

This reverts commit f89d26e.

This should now be safe to merge, as getsentry has already been bumped
to 22.16

@joshuarli this change picks the .volta.json -> .node-version change,
but does not actually remove the .volta.json
getsentry-bot added a commit that referenced this pull request Jun 17, 2025
JonasBa added a commit that referenced this pull request Jun 17, 2025
billyvg pushed a commit that referenced this pull request Jun 18, 2025
billyvg pushed a commit that referenced this pull request Jun 18, 2025
This reverts commit 4df68a9.

Co-authored-by: asottile-sentry <[email protected]>
billyvg pushed a commit that referenced this pull request Jun 18, 2025
Reapply node version bump, but preserve .volta.json so we can maintain
backcompat with getsentry
billyvg pushed a commit that referenced this pull request Jun 18, 2025
billyvg pushed a commit that referenced this pull request Jun 18, 2025
…3698)

This reverts commit f89d26e.

This should now be safe to merge, as getsentry has already been bumped
to 22.16

@joshuarli this change picks the .volta.json -> .node-version change,
but does not actually remove the .volta.json
billyvg pushed a commit that referenced this pull request Jun 18, 2025
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
This reverts commit 4df68a9.

Co-authored-by: asottile-sentry <[email protected]>
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
Reapply node version bump, but preserve .volta.json so we can maintain
backcompat with getsentry
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
…3698)

This reverts commit f89d26e.

This should now be safe to merge, as getsentry has already been bumped
to 22.16

@joshuarli this change picks the .volta.json -> .node-version change,
but does not actually remove the .volta.json
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components Trigger: Revert Add to a merged PR to revert it (skips CI)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants